Hi,

I have set up SCCM 2012 r2 CU3 in our test environment.  From my single primary site server I can push the SCCM client installation.  

However i have downloaded MS updates, placed them in software update groups and deployed these groups.  The clients realize they have updates to install but almost immediately go to the status of FAILED.  Before my updates were showing "DOWNLOADING 0%" (and would sit at this 0% for hours, never increasing) and at the suggestion of others I changed my boundary group from a IP Subnet to an IP RANGE.  Since that change they immediately fail.

The SCCM Site server sits on the same subnet as my test clients with no ACLs in place so no ports or traffic being blocked.  If there is a particular log file that would help in resolving this let me know please.

I do have certs set up with my server and I do have the domain gpo setting to "specify intranet microsoft update service location" set to "https://SCCM01.local.lcl:8531"

• Edited by thedietz Tuesday, January 13, 2015 3:56 PM

whether it helps or not i should also say that my SCCM server also realizes it has updates to install, but they also go directly to "failed".  not sure if that info helps or not.

Hi

You need to delete your GPO specifying your WSUS. This information will be delivered to your clients via policy. After you done that you should try to force a Software Update Deployment cycle from one of your test clients and see what happens.

You can check the following log files on the client for errors related to Software Update Management:

PolicyEvaluator.log
Records details about the evaluation of policies on client computers, including policies from software updates.

ScanAgent.log
Records details about scan requests for software updates, the WSUS location, and related actions.

UpdatesDeployment.log
Records details about deployments on the client, including software update activation, evaluation, and enforcement. Verbose logging shows additional information about the interaction with the client user interface.

UpdatesHandler.log
Records details about software update compliance scanning and about the download and installation of software updates on the client.

WUAHandler.log
Records details about the Windows Update Agent on the client when it searches for software updates.

I have deleted the GPO, ran a gupdate /force on the client and had it check in for the updates.  It sees them but I am getting the same results, immediately going to failed.  Checking those logs I am only seeing errors in the updates handler log that read..

Unable to get locations, no need to continue with download UpdatesHandler 1/13/2015 1:19:35 PM 1496 (0x05D8)
CBundledUpdate -- Failed to download update (fb9ee84d-a2f0-4f3c-86fb-f6b407e4e6bf). Error = 0x87d00669 UpdatesHandler 1/13/2015 1:19:35 PM 1496 (0x05D8)
CDeploymentJob -- Failed to download update (022f39ad-6b5c-4f5a-8667-b25f2f3f0069). Error = 0x87d00669 UpdatesHandler 1/13/2015 1:19:35 PM 1496 (0x05D8)

Any help is greatly appreciated!!!!

• Edited by thedietz Tuesday, January 13, 2015 6:32 PM

Hi,

0x87d00669 Not able to get software update content locations at this time. 

Please make sure update content are distributed to DP successfully. Distmgr.log will help during this phase.

Also double check you have DP available for you boundary group.

Daniel,

Thank you very much!  I did not distribute the deployment packages to a distribution point.   I figured with having only one primary site server for SCCM and nothing else that everything was automatically assigned to my primary site server as the distribution point.  

Can i ask is there a good SCCM site to look up errors such as 0x87d00669?  I found many people commenting on this error, but you were the first to say "not able to get software update content locations at this time".  Maybe that just comes with experience?  I am not sure.

Thanks again!

cmtrace.exe -> Tools -> Error Lookup

That is great!!!!  THanks!!

Hi, I was deploying Windows Server 2012 R2 creating a reference image. So the machine was not a domain member. I ended up looking at the boundaries. The current boundary was based on an AD Site, so I added an IP subnet boundary to the Boundary Group in which the to be created machine was residing. After that, the machine was able to find the content.

Note: Strange thing is that Packages were deploying all the time without an issue and able to find content anyway.

• Edited by Nielsvd 17 hours 37 minutes ago